Network switching with co-resident data-plane and network interface controllers

ABSTRACT

A system with co-resident data-plane and network interface controllers embodying a method for network switching of a data packet outgoing from an internal facing interface of a network interface controller portion of the network interface resource to a network is disclosed.

BACKGROUND 1. Field

The present disclosure relates to communications in computer networks.More particularly, this invention is directed toward network switchingwith co-resident data-plane and network interface controllers.

2. Description of Related Technology

In modern communications networks, information (voice, video, data) istransferred among the nodes of the communications network in the form ofpacket data. A packet is a formatted unit of data carried by apacket-switched network. A packet consists of two kinds of data: controlinformation and user data (also known as payload). The controlinformation provides data the network needs to deliver the user data,for example: source and destination network addresses, error detectioncodes, and sequencing information. Typically, control information isfound in packet headers and trailers, with payload data in between.

In traditional computer systems, a computer is connected to acommunication network via a network interface controller (NIC). The NICcomprises a network facing physical port to connect to the communicationnetwork, an electronic circuitry required to communicate using aspecific physical layer and data link layer standards and an internalfacing physical interface allowing a driver to interface the NIC withthe computer. The electronic circuitry may comprise anapplication-specific integrated circuit (ASIC). An ASIC comprises anintegrated circuit (IC) customized for a particular use, rather thanintended for general-purpose use.

The packet processing at the NIC is interrupt driven. Interrupt is asignal to the processor emitted by hardware or software, indicating anevent that needs immediate attention. Consider, by means of an example,an incoming packet arriving at the NIC. The NIC writes the packet into athe NIC's memory; ascertains that the packet is valid by performingverification, e.g., a Cyclic Redundancy Check (CRC), and then sends thepacket to the computer's memory buffer requested by a driver from andallocated by a kernel. A the kernel is a computer program that managesinput/output requests from software, and translates them into dataprocessing instructions for the central processing unit and otherelectronic components of a computer. The kernel is a fundamental part ofa modern computer's operating system. After the buffer has beenallocated, the driver provides the address of the computer's memorybuffer to the NIC. After writing the packet to the computer's memorybuffer, the NIC sends an interrupt to the kernel. The kernel responds byservicing the interrupt, with all the overhead associated with theinterrupt, i.e., suspending current activities, saving the currentactivities state, and executing an interrupt handler routine. Thisinterruption is temporary, and, after the interrupt handler routinefinishes, the processor resumes normal activities.

The interrupt handler routine carries out packet processing related topacket management, e.g., switching/routing, packet/frame discrimination,Quality of service (QoS) enforcement, access control, encryption,Transmission Control Protocol (TCP) offload processing, and other packetmanagement known to a person skilled in the art, and delivers the packetto the destination entity.

The packet management is implemented in the kernel's software, and sincethe kernel software runs on a general purpose processor, the softwareimplementation has low performance. Coupled with the interrupt overhead,the packet processing using the NIC negatively affects networkperformance, e.g., throughput, latency, and other network performancecriteria known to a person of ordinary skill in the art.

Based on the foregoing, usage of traditional computer systems forgeneral packet management, is inefficient. To solve at least some of theproblems, network processors, which comprise software programmablehardware devices, often implemented as integrated circuits (IC) havebeen developed. Network processors have specific features orarchitectures optimizing packet processing within the communicationnetworks. Such packet processing may comprise e.g., pattern matching,key lookup, data bit-field manipulation, queue management, controlprocessing, and other processing known to a person of ordinary skill inthe art.

Using the specific function of the network processor, the softwareprogram implements an application that the network processor executes,resulting in the piece of physical equipment performing a task orproviding a service. Such applications may comprise, e.g.,switching/routing, packet/frame discrimination, Quality of service (QoS)enforcement, access control, encryption, Transmission Control Protocol(TCP) offload processing, and other applications known to a personskilled in the art.

In addition, network processors use data-plane architecture that definesthe processing of the packets arriving on an inbound interface todetermine the path from the internal data-plane fabric to the properoutgoing interface(s). To support such architecture, the networkprocessors employ event driven processing. An event is an action oroccurrence detected by a system entity that then transfers the event toanother entity that is a consumer of the event. The consumer entityeventually applies a reaction to the event. Unlike an interrupt that maydemand immediate service at any time, events are normally handledsynchronously, i.e., the system explicitly waits for an event to beserviced (typically by calling an instruction that dispatches the nextevent). Since the event is serviced after a previous event has finished,the overhead associated with interrupt processing is avoided.

Considering, by means of an example, an incoming packet arriving at thenetwork processor inbound interface. The inbound interface writes thepacket into a memory; ascertains that the packet is valid by performingverification, e.g., a Cyclic Redundancy Check (CRC) and then sends thepacket to the computer's memory buffer requested by the interface andallocated by a memory manager. After the buffer has been allocated, thememory manager provides the address of the memory to the processornetwork inbound interface, which writes the packet to the computer'smemory. After writing the packet to the computer's memory, the inboundinterface generates an event. The event is provided to an event handlingentity, e.g., via a scheduler, that schedules the event processing bythe packet destination entity.

When the destination entity is ready to carry the processing of thepacket, the entity requests an event from the event handling entity. Theevent handling entity then provides the event caused by the packet, andthe destination entity carries out the packet processing.

Optionally, the event handling entity may carry out processing relatedto packet management, e.g., packet/frame discrimination, Quality ofservice (QoS) enforcement, access control, encryption TransmissionControl Protocol (TCP) offload processing, and other packet managementknown to a person skilled in the art, and delivers the packet to thedestination entity. Since the packet management is implemented using thespecific function of the network processor, the implementation has highperformance.

Current computer systems increasingly employ virtualization, i.e., aprocess by which a virtual version of computing resources, such ashardware and software resources, i.e., a central processor unit, astorage system, an input/output resources, a network resource, anoperating system, and other resources known in the art, are simulated bya computer system, referred to as a host machine. A typical host machinemay comprise a hardware platform that optionally together with asoftware entity, i.e., an operating system, operates a hypervisor, whichis software or firmware that creates and operates virtual machines, alsoreferred to as guest machines. Through hardware virtualization, thehypervisor provides each virtual machine with a virtual hardwareoperating platform. By interfacing with the virtual hardware operatingplatform, the virtual machines access the computing resources of thehost machine to execute virtual machines' respective operations. As aresult, a single host machine can support multiple virtual machines,each operating an operating system and/or other software entity, i.e.,an application, simultaneously through virtualization.

FIG. 1 depicts a conceptual structure of a virtualization system 100. Ahardware platform 102 comprises all physical entities embodyingcomputing resources required by a specific host machine, i.e., a centralprocessor unit, an input/output resource, a storage system, a networkresource, and other resources known to a person having ordinary skill inthe art. To avoid undue complexity, only a storage system 104, a networkresource 106, are shown. The storage system 104, may comprise a harddrive, a semiconductor based memory, and other types of memory known inthe art. The terms storage system and memory are used interchangeably.The network resource 106 may comprise at least one NIC.

The hardware platform 102, together with an optional software entity108, i.e., operating system, comprises a host machine operating a Type 2hypervisor, also known as hosted hypervisor 110. As well known to aperson having ordinary skill in the art, the optional software entity108 is not necessary for Type 1 hypervisor, also known as nativehypervisor. A hypervisor is software or firmware entity that creates andoperates at least one virtual machine, also referred to as a guestand/or a guest machine. As depicted in FIG. 1, the hosted hypervisor 110created and operates three virtual machines 112; however differentnumber of virtual machines, including a single virtual machine, iscontemplated. Through hardware virtualization, the hosted hypervisor 110provides each virtual machine 112 with a virtual hardware operatingplatform. By interfacing with the virtual hardware operating platform,the virtual machines 112 access the computing resources of the hostmachine to execute the virtual machines' respective operations. As aresult, a single host machine can support multiple virtual machines 112,each operating an operating system and/or other software entity, i.e.,an application, collectively shown as 116 simultaneously throughvirtualization. Parameters configuring operation of the virtual machine112 are defined via structure 114. In an aspect, the structure 114 maycomprise at least one register.

To enable transfer of data packets into and from the virtualizationsystem 100, via network resource 106, as well as routing the datapackets among different entities of the virtualization system 100 viainternal network, using interrupt driven kernel packet management maydegrade network performance. Additionally, divorcing the packet routingand management functionality from the kernel's functionality enables therouting and management functionality to be developed and providedwithout dependence of a specific kernel's implementation.

Accordingly, there is a need in the art for a packet management,providing a solution to the above identified problems, as well asadditional advantages.

SUMMARY

In an aspect of the disclosure, an apparatus with co-resident data-planeand network interface controllers implementing a method for networkswitching according to appended independent claims is disclosed.Additional aspects are disclosed in the dependent claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing aspects described herein will become more readily apparentby reference to the following description when taken in conjunction withthe accompanying drawings wherein:

FIG. 1 depicts a conceptual structure of a virtualization system inaccordance with known aspects;

FIG. 2 depicts a conceptual structure of a network interface resourcesin accordance with an aspect of this disclosure;

FIG. 3a depicts a first part of a flow chart enabling the process forswitching between a NIC and a Packet input processor (PKI)/Packet outputprocessor (PKO) for incoming packet in accordance with an aspect of thisdisclosure;

FIG. 3b depicts a second part of the flow chart enabling the process forswitching between a NIC and a Packet input processor (PKI)/Packet outputprocessor (PKO) for incoming packet in accordance with an aspect of thisdisclosure;

FIG. 4a depicts a first part of a flow chart enabling the process forswitching between the NIC and the PKI/PKO for outgoing packet inaccordance with an aspect of this disclosure;

FIG. 4b depicts a second part of the flow chart enabling the process forswitching between the NIC and the PKI/PKO for outgoing packet inaccordance with an aspect of this disclosure.

The description of like structural elements among the figures, is notrepeated, the like elements have reference numerals differing by aninteger multiple of 100, i.e., reference numeral 102 in FIG. 1, becomesreference numeral 202 in FIG. 2; unless differences and/or alternativeaspects are explicitly noted. An expression “_X” in a referenceindicates an instance of an element, while and expression “(X)”indicates a sub-block in a drawing where helpful for betterunderstanding. Any unreferenced single and/or double-arrow lineindicates a possible information flow between the depicted entities.

DETAILED DESCRIPTION

Unless otherwise defined, all terms (including technical and scientificterms) used herein have the same meaning as commonly understood by aperson having ordinary skill in the art to which this invention belongs.It will be further understood that terms, such as those defined incommonly used dictionaries, should be interpreted as having a meaningthat is consistent with their meaning in the context of the relevant artand this disclosure.

As used herein, the singular forms “a,” “an,” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprise,”“comprises,” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,elements, components, and/or groups thereof. The term “and/or” includesany and all combinations of one or more of the associated listed items.

The term “communicatively coupled” is intended to specify acommunication path permitting information exchange either directly amongthe communicatively coupled entities, or via an intervening entity.

Various disclosed aspects may be illustrated with reference to one ormore exemplary configurations. As used herein, the term “exemplary”means “serving as an example, instance, or illustration,” and should notnecessarily be construed as preferred or advantageous over otherconfigurations disclosed herein.

Various aspects of the present invention will be described herein withreference to drawings that are schematic illustrations of conceptualconfigurations of the present invention, unless explicitly noted. Thevarious aspects of this disclosure are provided to enable a personhaving ordinary skill in the art to practice the present invention.Modifications to various aspects of a presented throughout thisdisclosure will be readily apparent to a person having ordinary skill inthe art, and the concepts disclosed herein may be extended to otherapplications.

FIG. 2 depicts a conceptual structure of a network interface resources206 in accordance with an aspect of this disclosure. The structure 206provides at least a NIC 218, a packet input processor (PKI) 220, and apacket output processor (PKO) 222 on a single chip, designed to minimizepower consumption, chip area, input output, pin-out and other chipcharacteristics. Thus, the structure does not simply place twoindividual chips on a single piece of silicon material. A chip comprisesa semiconductor material, onto which a set of electronic circuits isfabricated. A data packet from a communications network (not shown)arrives via one of physical connectors/ports 224 and is provided tocommunicatively coupled medium access controller (MAC) 226, hardware ora hardware and software entity that implements a media access controldata communication protocol. In one aspect, the MAC 226 is also providedon the chip. The MAC 226 emulates a full-duplex logical communicationchannel in a multi-point network and provides the data packet to eitherthe NIC 218 or the PKI 220. Although only two physical connectors/ports224 and MACs 226 are shown, other number of ports and MACs arecontemplated.

In one aspect, the MAC 226 selects the NIC 218 or the PKI 220 based on avalue in a register (not shown), thus statically assigning the MAC 226to either the NIC 218 or the PKI 220. In computer architecture, aprocessor register is a small amount of storage available as part of aCPU or other digital processor. Such registers are (typically) addressedby mechanisms other than main memory and can be accessed more quickly.Such a static assignment may be used to associate a connector/port,e.g., 224(1), with the NIC 218, e.g., because the connector/port 224(1)is already preceded with a router/switch using a network processorcarrying efficiently packet management.

In another aspect, the MAC 226 selects the NIC 218 or the PKI 220 inaccordance with a content of the data packet, e.g., a source address, adestination address, or any other content known to a person of ordinaryskill in the art.

In yet another aspect, the MAC 226 selects the NIC 218 or the PKI 220 inaccordance the combination of the aspects.

Consider first that the MAC 226 selects the NIC 218. The data packet isprovided via a network facing inbound interface to a parser 218(1),which, parses the data packet in accordance with an implementation ofany of the family of computer networking technologies, e.g., anEthernet, an Internet Protocol (IP), the TCP, and other computernetworking technologies known to a person of ordinary skill in the art,to determine the type of protocol used, and to apply some packetmanagement, e.g., Quality of Service (QoS) to the data packets. The NIC218 ascertains that the packet is valid by performing verification,e.g., a Cyclic Redundancy Check (CRC). The NIC 218 then requests amemory manager 228 to allocate a portion of a storage 204/205 to receivethe data packet and additional information to another portion of thestorage 204/205. The additional information may comprise a completepacket descriptor, or a list of commands which form a packet descriptor.The packet descriptor information may comprise, e.g., information atwhich addresses in the storage 204/205, the different parts of the datapacket, e.g., a header, payload, are located, and other informationknown to a person of ordinary skills in the art. The allocated portionof a storage may comprise e.g., a buffer, i.e., a region of a physicalstorage used to temporarily store data while it is being moved from oneplace to another. The double reference 204/205 is meant to indicate thatthe storage may be distributed between chip comprising the networkinterface resources 206, identified by reference 205, and an off chipstorage, identified by reference 204 residing on the system served bythe network interface resources 206.

Once the storage 204/205 has been allocated, the NIC 218 writes the datapacket and the additional information to the allocated portion of thestorage 204/205. In one aspect, the NIC 218 may use e.g., Direct MemoryAccess (DMA) engine 218(2), which allows the storage 204/205 to beaccessed independently of a central processing unit. In accordance withan implementation trading throughput against latency, the NIC 218 sendsan interrupt to a kernel. Thus, in one aspect, when latency is critical,the NIC 218 may send the interrupt after processing each packet; inanother aspect, the NIC 218 may accumulate several packets into thestorage 204/205 before sending the interrupt.

The kernel executes an interrupt handler routine, packet processingrelated to packet management, e.g., switching/routing, packet/framediscrimination, Quality of service (QoS) enforcement, access control,encryption, Transmission Control Protocol (TCP) offload processing,routing, and other packet management known to a person skilled in theart, determines and delivers the data packet to the destination entity230. The destination entity 230 may comprise a component of the kernel,the operating system, and any other entity of the system served by thenetwork interface resources 206. At the destination entity 230 thedelivered packet is placed to a queue (not shown) for processing.Methods for queue management, e.g., a tail drop, a backpressure, arandom early discard, a Quality of Service by the destination entity 230are well known by a person of ordinary skill in the art. A queue is anorganization of data into a structure in which entities, i.e., the datacomprising a packet, are kept and are retrievable in a definite order.

When the entity 230 needs to send a data out over the communicationnetwork, in one aspect the entity 230 requests the memory manager 228 toallocate a portion of the storage 204/205 to receive a complete packetdescriptor, or a list of commands which form a packet descriptor, andnotifies the transmit DMA engine 218(3). In another aspect, the entity230 requests the kernel to process the data for a transmission. Inresponse, the kernel requests the memory manager 228 to allocate aportion of the storage 204/205 to receive a complete packet descriptor,or a list of commands which form a packet descriptor, and notifies thetransmit DMA engine 218(3). In yet another aspect, the entity 230requests the kernel to process the data for a transmission. In response,the kernel allocates a portion of the storage 204/205 to receive acomplete packet descriptor, or a list of commands which form a packetdescriptor, and notifies the transmit DMA engine 218(3). The DMA engine218(3) reads the packet descriptors and provides the data packet via anetwork facing outgoing interface to the MAC 226. Alternatively, the DMAengine 218(3) executes the list of commands, assembles a packet from thedata, and provides the data packet to the MAC 226. MAC 226 thentransmits the data packet to the communication network via the physicalconnectors/ports 224(1).

Consider now that the MAC 226 selects the PKI 220. The data packet isprovided a network facing interface to a parser 220(1), which parses thedata packet in accordance with an implementation of any of the family ofcomputer networking technologies, e.g., an Ethernet, Internet Protocol(IP), the TCP, and other computer networking technologies known to aperson of ordinary skill in the art. In accordance with parametersobtained from fields of the parsed data packet, the PKI 220 determines asoftware or hardware entity, e.g., the entity 232 to receive and processthe data packet. The parameters may comprise, e.g., a port at which theincoming packet was received, a destination MAC address, a destinationIP address, and other fields known to a person skilled in the art. Theentity 232 may comprise, e.g., an operating system, an applicationexecuted by the operating system, such application including a virtualmachine, a hard disk, or any other entity known to a person of ordinaryskill in the art.

The PKI 220 then requests the memory manager 228 to allocate a portionof a storage 204/205 to receive the data packet. Such a portion of amemory may comprise e.g., a buffer. Once the PKI 220 writes the datapacket via an inside facing interface to the allocated portion of thestorage 204/205, the PKI 220 provides an event notification to a packethandling software entity 234 that a data packet for the entity 232 isavailable. Such notification may comprise providing information topacket handling software entity 234 via a scheduler (not shown). Oncethe software entity 232 is ready to obtain work involving the datapacket, the software entity 232 requests work from the scheduler. Theterm work is any operation to be carried out by the software entity 232.The scheduler retrieves the work, in form of the instructions to beprocessed and an address to the data packet(s) on which the work is tobe carried out, and provides the work to the entity 232. The entity 232then requests the data packet from the storage 204/205 and the datapacket is processed by the packet handling software entity 234, whichprocesses the packet in accordance with a packet management policy, andprovides the packet to the entity 232, if the policy allows suchdelivery.

In one aspect, the packet handling software entity 234 may implementfunctionality related to packet management, e.g., layer 2 (L2)switching, layer 3 (L3) switching, traffic policing, access control,traffic shaping, deep packet inspection, and other packet managementknown to a person of ordinary skill in the art.

As appreciated by a person of ordinary skill in the art, L3 switchinguses the MAC address from the host's network interface resource todecide where to forward frame. L3 uses a routable protocol address fromthe frame. Such routable protocol may comprise, e.g., IP, InternetworkPacket Exchange (IPX), AppleTalk, and other known to a person ofordinary skill in the art. In traditional systems, the switchingfunctionality is implemented in a hardware, i.e., in an ApplicationSpecific Integrated Circuit (ASIC). Such an ASIC is not necessary in anaspect of the invention. Since the packet handling software entity 234is implemented on an already existing hardware, i.e., a coprocessor, ofthe network interface resource 206, the functionality related to packetmanagement may be implemented as additional software on the hardware.Thus, there may be no hardware cost in term of, e.g., additional chiparea, power consumption, to this packet management function. Acoprocessor is a computer processing unit used to supplement thefunctions of the central processing unit. Supplemental functionsperformed by the coprocessor may be floating point arithmetic, graphics,signal processing, string processing, encryption or I/O Interfacing withperipheral devices. The coprocessor carries out these functions under aclose control of a supervisory processing unit.

When the entity 232 needs to send a data out over the communicationnetwork, the entity 232 requests the memory manager 228 to allocate aportion of the storage 204/205 to receive a complete packet descriptor,or a list of commands which form a packet descriptor, and notifies thePKO's 222 transmit DMA engine 222(2). The DMA engine 222(2) reads thepacket descriptors via the PKO's 222 inside facing interface andprovides the data packet to the MAC 226. Alternatively, the DMA engine222(2) executes the list of commands, assembles a packet from the data,and provides the data packet via the PKO's 222 network facing interfaceto the MAC 226. MAC 226 then transmits the data packet to thecommunication network via the physical connectors/ports 224.

The conceptual structure 206 providing at least NIC and PKI/PKO on asingle chip enables use of the chip in applications requiring use ofboth the NIC and PKI/PKO. By means of an example, consider a virtualizedsystem 100 disclosed in FIG. 1. The operating system 108 may need to usethe NIC portion of the network resource 106, while the virtual machine112(1), which instantiates a data-plane may need to use the PKI/PKOportion of the network resource 106. Additionally, the chip allowsproviding packet management, including switching of a packet to theoperating system 108, and/or other entities communication via a kernel,even if the packet arrives at the PKI/PKO portion of the networkresource 106. Such a functionality may allow a packet intended for aplurality of destinations, e.g., a broadcast packet, a multicast packet,to reach all destinations. In addition, even if an entity, e.g., avirtual machine 112(2), is capable of instantiating a data-plane, theentity may still prefer to receive packets via the NIC portion of thenetwork resource 106, because due to the difference in interrupt drivensoftware, i.e., operating system, and event driven software, i.e.,data-plane, the application execution on the virtual machine 112(2) maybetter use the kernel's capabilities. Thus, the packet may be directedto the PKI/PKO portion of the network resource 106, use some of theefficient packet management functionality of the network processor, andthen be routed via the NIC portion of the network resource 106 to usethe kernel's capabilities.

Referring back to the conceptual structure 206, to enable communicationbetween the NIC 218 and the PKI 220 respective PKO 222, hardwareloopback entities 236, 238 are provided.

FIG. 3 depicts a flow chart enabling the process for switching betweenthe NIC and PKI/PKO for incoming packet. To further clarify therelationship between the flow chart of FIG. 3 and certain elements ofthe conceptual structure of a virtualization system 100 disclosed ingreater details in FIG. 1 and associated text, and the network resource206 as disclosed in FIG. 2 and associated text, references to thestructural elements are in parenthesis.

In step 302, a hypervisor (110) initiates entities that configure aspecific operation of the virtual system (100), e.g., the hypervisor(110), the virtual machine(s) (112), i.e., structures (114), and thenetwork resources, (106), i.e., register (114). The process continues instep 304.

In step 304, a data packet from a communications network arrives via oneof physical connectors/ports (224_n) and is provided to a MAC (226). Theprocess continues in step 306.

In step 306, the MAC (226) determines whether the packet should beprovided to a NIC (218) or to the PKI (220). The determination iscarried out in accordance with a specific implementation.

Thus, in one aspect, the MAC (226) selects the NIC (218) or the PKI(220) in accordance with a content of the data packet, e.g., a sourceaddress, a destination address, or any other content known to a personof ordinary skill in the art.

In another aspect, the MAC (226) determines a value of the variable inthe register (114). When the variable has a first value, the MAC (226)selects the NIC (218); when the variable has a second value, the MAC(226) selects the PKI (220).

In yet another aspect, the variable in the register (114) is amulti-state variable. When the variable has a first value, the MAC (226)selects the NIC (218); when the variable has a second value, the MAC(226) selects the PKI (220); and when the variable has a third value,the decision is carried out in accordance with the content of the datapacket.

A person skilled in the art will appreciate that other implementationsof the decision process are within the scope of the invention.

The process continues in step 308 when the MAC (226) determined that thepacket is to be delivered to the NIC (218), and the process continues instep 314 when the MAC (226) determined that the packet is to bedelivered to the PKI (220).

In step 308, the packet is delivered to the NIC (218). The processcontinues in step 310.

In step 310, the NIC (218) processes the packet as disclosed infra andsends an interrupt to a kernel. The process continues in step 312.

In step 312, the kernel processes the packet as disclosed infra, anddelivers the data packet, to a queue of the destination entity (230) forprocessing as disclosed infra.

In step 314, the packet is delivered to the PKI (220). The processcontinues in step 316.

In step 316, the PKI (220) processes the packet to determines a targetsoftware or hardware entity (230) to receive and process the data packetas disclosed infra. The process continues in step 318.

In step 318, the data packet is written to the allocated portion of thememory (204/205), and packet handling software entity (234) is notifiedthat a data packet for the entity (232) is available as disclosed infra.The process continues in step 320.

In step 320, the target software or hardware entity (230) that hasobtained work involving the data packet requests the data packet(s) fromthe packet handling software entity (234) as disclosed infra. Theprocess continues in step 322.

In step 322, the packet handling software entity (234) processes thepacket in accordance with a packet management policy. The packetmanagement policy for the packet is determined in accordance withcriteria that may be based on the fields in the packet, the rate of atraffic, and other criteria known to a person of ordinary sill in theart. By means of an example, the fields in the packet, e.g., the sourceor the destination MAC or IP address may be used for access control; thedata portion, and possibly the header of the packet may be used for deeppacket inspection for protocol non-compliance, viruses, spam,intrusions, or defined criteria to decide whether the packet may bepassed, be discarded, or be re-routed to a different destination. Bymeans of another example, the rate of the traffic may be used fortraffic policing, and/or traffic shaping. The process continues in step324 when the packet handling software entity (234) determines that thepacket need to be discarded or be re-routed to a different destination;otherwise, the process continues in step 326.

In step 324, the packet is dropped or re-routed to another entity, e.g.,an intrusion detection entity.

In step 326, if the PKI (220) determined that target entity to receivethe packet is an entity, which instantiated a data-plane and theprocessing continues in step 328. Otherwise the packet is provided tothe PKO (222), and the processing continues in step 330.

In step 328, the packet is delivered to the target entity.

In step 330, the packet is processed by the PKO (222) as disclosedinfra. The process continues in step 332.

In step 332, the PKO (222) provides the packet to the NIC (218) via aloopback entity (236) the since the destination entity (230) to receiveand process the data packet is incapable of, or does not instantiate adata-plane. The processing continues in step 334.

In step 334, the NIC (218) processes the data packet as disclosed infraand sends an interrupt to a kernel. The process continues in step 336.

In step 336, the kernel processes the packet as disclosed infra, anddelivers the data packet, to a queue of the destination entity (230) forprocessing as disclosed infra. The process ends.

FIG. 4 depicts a flow chart enabling the process for switching betweenthe NIC and PKI/PKO for outgoing packet. To further clarify therelationship between the flow chart of FIG. 4 and certain elements ofthe conceptual structure of a virtualization system 100 disclosed ingreater details in FIG. 1 and associated text, and the network resource206 as disclosed in FIG. 2 and associated text, references to thestructural elements are in parenthesis.

In block 402, a hypervisor (110) initiates entities that configure aspecific operation of the virtual system (100), e.g., the hypervisor(110), the virtual machine(s) (112), i.e., structures (114), and thenetwork resources, (106), i.e., register (114). The process continues inblock 404.

In block 404, an entity in of the virtual system (100), e.g., an entity(230) running as a guest on virtual machine (112(1)), needs to send adata out over the communication network. In one aspect, the requests thememory manager (228) to allocate a portion of the storage (204/205) toreceive a complete packet descriptor, or a list of commands which form apacket descriptor, and notifies the NIC (218), e.g., the transmit DMAengine (218(3)). The process continues in block 408. In another aspect,the entity (230) requests the kernel to process the data for atransmission. The process continues in block 406.

In block 406, the kernel requests the memory manager (228) to allocate aportion of the storage (204/205) to receive a complete packetdescriptor, or a list of commands which form a packet descriptor, andnotifies the NIC (218), e.g., the transmit DMA engine (218(3)). Theprocess continues in block 408.

In block 408, the DMA engine 218(3) reads the packet descriptors or,alternatively, executes the list of commands and assembles a packet fromthe data, and provides the data packet via the loopback entity (238) tothe PKI (220). The process continues in block 410.

In block 410, the PKI (220) processes the packet to determine a targetsoftware or hardware entity to receive and processes the data packet asdisclosed infra. When the PKI (220) determines that the target softwareor hardware entity is within the virtual system (100), e.g., an entity(232) running as a guest on virtual machine (112(2)), the processcontinues in block 412; otherwise the process continues in block 422.

In block 412, the data packet is written to the allocated portion of thememory (204/205), and packet handling software entity (234) is notifiedthat a data packet for the entity (232) is available as disclosed infra.The process continues in step 414.

In step 414, the target software or hardware entity (232) that hasobtained work involving the data packet requests the data packet(s) fromthe packet handling software entity (234) as disclosed infra. Theprocess continues in step 416.

In step 416, the packet handling software entity (234) processes thepacket in accordance with a packet management policy. The packetmanagement policy for the packet is determined in accordance withdifferent criteria. Such criteria may be based on the fields in thepacket, the rate of a traffic, and other criteria known to a person ofordinary sill in the art. by means of an example, the fields in thepacket, e.g., the source or the destination MAC or IP address may beused for access control; the data portion, and possibly the header ofthe packet may be used for deep packet inspection for protocolnon-compliance, viruses, spam, intrusions, or defined criteria to decidewhether the packet may be passed, be discarded, or be re-routed to adifferent destination. By means of another example, the rate of thetraffic may be used for traffic policing, and/or traffic shaping. Theprocess continues in step 418 when the packet handling software entity(234) determines that the packet need to be discarded or be re-routed toa different destination; otherwise, the process continues in step 420.

In step 418, the packet is dropped or re-routed to another entity, e.g.,an intrusion detection entity.

In step 420, the packet is delivered to the queues of the target entity(232).

In step 422, the packet is delivered to the packet handling softwareentity (234). The process continues in block 424.

In step 424, the packet handling software entity (234) processes thepacket in accordance with a packet management policy. The packetmanagement policy for the packet is determined in accordance withcriteria that may be based on the fields in the packet, the rate of atraffic, and other criteria known to a person of ordinary sill in theart. by means of an example, the fields in the packet, e.g., the sourceor the destination MAC or IP address may be used for access control; thedata portion, and possibly the header of the packet may be used for deeppacket inspection for protocol non-compliance, viruses, spam,intrusions, or defined criteria to decide whether the packet may bepassed, be discarded, or be re-routed to a different destination. Bymeans of another example, the rate of the traffic may be used fortraffic policing, and/or traffic shaping. The process continues in step418 when the packet handling software entity (234) determines that thepacket need to be discarded or be re-routed to a different destination;otherwise, the process continues in step 426.

In step 426, the packet is delivered to the PKO (222). The processcontinues in step 428.

In step 428, the packet is processed by the PKO (222) as disclosedinfra. The process continues in step 430.

In step 430, the PKO (222) provides the packet to the output port (224)via the MAC (226), since the destination entity to receive and processthe data packet is outside the virtual system (100). The process ends.

The various aspects of this disclosure are provided to enable a personhaving ordinary skill in the art to practice the present invention.Various modifications to these aspects will be readily apparent topersons of ordinary skill in the art, and the concepts disclosed thereinmay be applied to other aspects without departing from the spirit orscope of the invention. Thus, the present invention is not intended tobe limited to the aspects shown herein but is to be accorded the widestscope consistent with the principles and novel features disclosedherein.

Therefore, by means of an example a person having ordinary skill in theart will understand, that the flow chart is not exhaustive becausecertain steps may be added or be unnecessary and/or may be carried outin parallel based on a particular implementation.

All structural and functional equivalents to the various illustrativelogical blocks, modules, circuits, and algorithm steps described inconnection with the various aspects described throughout this disclosurethat are known or later come to be known to those of ordinary skill inthe art are expressly incorporated herein by reference and are intendedto be encompassed by the claims. Such illustrative logical blocks,modules, circuits, and algorithm steps may be implemented as electronichardware, computer software, or combinations of both.

Those of skill in the art would understand that information and signalsmay be represented using any of a variety of different technologies andtechniques. For example, data, instructions, commands, information,signals, bits, symbols, and chips that may be referenced throughout theabove description may be represented by voltages, currents,electromagnetic waves, magnetic fields or particles, optical fields orparticles, or any combination thereof.

Moreover, nothing disclosed herein is intended to be dedicated to thepublic regardless of whether such disclosure is explicitly recited inthe claims. No claim element is to be construed under the provisions of35 U.S.C. § 112, sixth paragraph, unless the element is expresslyrecited using the phrase “means for” or, in the case of a method claim,the element is recited using the phrase “step for.”

What is claimed is:
 1. A method for network switching with co-residentdata-plane processors and network interface controller, comprising:receiving an outgoing packet at an internal facing interface of anetwork interface controller portion of a network interface resourcecomprising: a data-plane packet input processor, a data-plane packetoutput processor, and the network interface controller, implemented on achip; providing the outgoing packet processed by the network interfacecontroller to the data-plane packet input processor; determining by thedata-plane packet input processor a target entity; and providing thepacket to the target entity according to the determination.
 2. Themethod as claimed in claim 1, wherein providing the packet processed bythe network interface controller to the data-plane packet inputprocessor comprises: providing the packet processed by the networkinterface controller to the data-plane packet input processor via aloopback entity.
 3. The method as claimed in claim 1, wherein providingthe packet to the target entity according to the determinationcomprises: providing the packet to a packet handling entity; andprocessing the packet in accordance with a packet management policy atthe packet handling entity.
 4. The method as claimed in claim 3, whereinthe processing the packet by a packet handling entity in accordance witha packet management policy comprises: discarding the packet.
 5. Themethod as claimed in claim 3, wherein the processing the packet by apacket handling entity in accordance with a packet management policycomprises: providing the packet to a different destination than thetarget entity.
 6. The method as claimed in claim 3, wherein theprocessing the packet in accordance with a packet management policy atthe packet handling entity comprises: providing the processed packet toa network via the data-plane packet output processor.
 7. The method asclaimed in claim 1, wherein providing the packet to the target entityaccording to the determination comprises: providing the packet processedby the data-plane packet input processor to a storage; requesting thepacket by the target entity; and processing the packet by a packethandling entity in accordance with a packet management policy.
 8. Themethod as claimed in claim 7, wherein the processing the packet inaccordance with a packet management policy at the packet handling entitycomprises: providing the processed packet to the target entity.
 9. Themethod as claimed in claim 7, wherein the processing the packet by apacket handling entity in accordance with a packet management policycomprises: providing the packet to a different destination than thetarget entity.
 10. The method as claimed in claim 7, wherein theprocessing the packet by a packet handling entity in accordance with apacket management policy comprises: discarding the packet.